Closes: #9839

Description

This PR increases the app's resilience when Product or ProductVariation fields that expect a Bool receive a String instead:

• backordersAllowed
• onSale

It uses failsafe decoding to handle those alternative types, and adds to the unit tests for parsing alternative types. (These are known decoding errors that users have experienced for these fields.)

Testing instructions

We don't know the exact plugins that can cause this behavior, but you can test using a tool like Charles Proxy or Proxyman to intercept and modify the response:

1. Set a breakpoint in your tool of choice for requests to the /wc/v3/products endpoint.
2. Build and run the app.
3. Open the Products tab.
4. Modify the response in one or more of the following ways:
   • A product's backorders_allowed field returns a string representing a boolean value (e.g. "backorders_allowed": "1").
   • A product's on_sale field returns a string representing a boolean value (e.g. "on_sale": "0").
5. Execute the response and confirm the app loads the product list.

You can repeat the same steps with the variations list for a variable product, modifying the same fields in the response for a variation.

• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.